-
Couldn't load subscription status.
- Fork 5.5k
Docs - fix typo #15040
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs - fix typo #15040
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 3 Skipped Deployments
|
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including You can disable this status message by setting the WalkthroughThe pull request involves a minor documentation update for the Pipedream Connect components in the Changes
Possibly related PRs
Suggested labels
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs-v2/pages/connect/components.mdx (1)
66-67: Consider these style improvements:
- To avoid repetition, consider rephrasing: "Once you have selected the app, you can list its triggers and/or actions."
- Add a comma before "and" in the compound sentence: "We'll list the actions for Gitlab, and we'll pass..."
-Once you have the app you want to use, now you can list the triggers and/or actions for that app. We'll list the actions for Gitlab and we'll pass the `name_slug` `gitlab` as the `app`. +Once you have selected the app, you can list its triggers and/or actions. We'll list the actions for Gitlab, and we'll pass the `name_slug` `gitlab` as the `app`.🧰 Tools
🪛 LanguageTool
[style] ~67-~67: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... for the app Once you have the app you want to use, now you can list the triggers and/...(REP_WANT_TO_VB)
[uncategorized] ~67-~67: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...t app. We'll list the actions for Gitlab and we'll pass thename_sluggitlabas ...(COMMA_COMPOUND_SENTENCE)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (1)
docs-v2/pages/connect/components.mdx(3 hunks)
🧰 Additional context used
🪛 LanguageTool
docs-v2/pages/connect/components.mdx
[style] ~67-~67: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... for the app Once you have the app you want to use, now you can list the triggers and/...
(REP_WANT_TO_VB)
[uncategorized] ~67-~67: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...t app. We'll list the actions for Gitlab and we'll pass the name_slug gitlab as ...
(COMMA_COMPOUND_SENTENCE)
🔇 Additional comments (2)
docs-v2/pages/connect/components.mdx (2)
20-20: LGTM! Good catch on the typo fix.
The section title has been correctly updated from "Getting stated" to "Getting started".
38-38: LGTM! Good cleanup of extra spaces.
The formatting has been improved by removing unnecessary spaces before "Here's the response:" in both instances.
Also applies to: 73-73
WHY
Summary by CodeRabbit